Enhanced In-device Coexistence Interference Avoidance Using Predetermined Downlink Channel

ABSTRACT

A method, system and device are provided for avoiding in-device coexistence interference between different radio technologies deployed in adjacent bands on the same device by allocating a non-interfering downlink signaling channel for downlink reception of interference avoidance instructions at the UE device. In operation, a user equipment device detects IDC interference and sends an IDC indication message to the radio network to get an appropriate solution, but instead of waiting at the current frequency to receive the IDC response from the radio network, the user equipment device moves to a non-interfering downlink signaling channel for downlink reception of interference avoidance instructions.

CLAIM OF PRIORITY

This application is a continuation and claims priority to U.S. patentapplication Ser. No. 13/194,380, filed on Jul. 29, 2011, the entirecontents of which are hereby incorporated by reference.

BACKGROUND

1. Field

In general, communications systems and methods for operating same aredisclosed. In one aspect, methods, systems and devices are disclosed formanaging coexistence interference between different radio technologiesdeployed in adjacent bands.

2. Description of the Related Art

The growing market of smart connected devices requires that the samedevice supports multiple radio technologies on the in-device platform.However, some configurations may cause severe performance degradationdue to mutual in-device coexistence (IDC) interference. For example,with devices that support both Long Term Evolution (LTE) and Industrial,Science and Medical (ISM) technologies (such as Bluetooth and/or WLAN)and/or Global Navigation Satellite System (GNSS) technologies, there areuse cases for concurrent operation of these radios. Coexistence issuesmay arise between ISM and/or GNSS technologies and LTE deployed inadjacent bands. As shown in Table 1 below, coexistence interference mayarise where ISM transmission creates interference to the LTE receiver,and may also arise where LTE transmission creates interference to theISM receiver.

TABLE 1 Interference of the LTE and ISM components on the in-deviceconfiguration LTE TDD (2.3-2.4 GHz, Band 40) ISM LTE UL (2.5-2.6 GHz,Band 7) (2.4-2.4835 GHz) Coexistence Rx Tx LTE: Interfered ISM: NormalTx Rx LTE: Normal ISM: Interfered

Similar coexistence issues may occur with devices that include both LTEand GNSS components. As shown in Table 2 below, when LTE and GNSScomponents are working on the same device, there may be interference dueto adjacent frequency band operation or harmonic frequencies whichcannot be avoided by the allocation of a guard band at the sub-harmonicfrequency.

TABLE 2 Interference of the LTE and GNSS component configuration on in-device LTE (777-787 MHz/746-756 MHz, Band 13) GNSS (788-798 MHz/758-768MHz, Band 14) (1575.42 MHz) Coexistence Tx Rx LTE: Normal GNSS:Interfered

As will be appreciated, there are challenges to using currentstate-of-the-art filter technology to address coexistence interferencesince filters do not provide sufficient rejection on the adjacentchannel interference. These challenges are particularly acute in thecase of these components configured in a single device where theinterference occurs when the LTE component is transmitting on thespecified bands. Accordingly, a need exists for improved method, systemand device for managing coexistence interference between different radiotechnologies. Further limitations and disadvantages of conventionalprocesses and technologies will become apparent to one of skill in theart after reviewing the remainder of the present application withreference to the drawings and detailed description which follow.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference is now made to the following drawings, in which:

FIG. 1 is a signal flow diagram illustrating how existing radio resourcemanagement signaling procedures may be used to address coexistenceinterference;

FIG. 2 is a signal flow diagram illustrating a radio resource controlsignaling call flow in accordance with selected embodiments;

FIG. 3 illustrates an example spectrum band allocation of LTE andnon-LTE components used in which a non-interfering downlink signalingchannel may be allocated;

FIG. 4 is a signal call flow diagram illustrating the sequentialmovement of a UE from a first channel through a non-interfering downlinksignaling channel to a second channel in accordance with selectedembodiments;

FIG. 5 is a signal call flow diagram illustrating the whole movement ofa UE from a first channel through a non-interfering downlink signalingchannel to a second channel in accordance with alternate embodiments;

FIG. 6 illustrates an example computer system that may be suitable forimplementing the in-device coexistence interference at a user device ornetwork node;

FIG. 7 is a diagram of a software environment that may be implemented ona user agent and/or network node operable for some of the variousembodiments of the disclosure; and

FIG. 8 is a schematic block diagram illustrating exemplary components ofa mobile wireless communications device which may be used with selectedembodiments.

DETAILED DESCRIPTION

A method, system and device are provided for avoiding in-devicecoexistence (IDC) interference between different radio technologiesdeployed on the same device. In selected embodiments, a method andapparatus are provided for allocating a non-interfering downlinksignaling channel for downlink reception of interference avoidanceinstructions at the UE device. In operation, a user equipment devicedetects IDC interference between a first radio component (e.g., LTEcomponent) and a second radio component (e.g., ISM component), such ascan occur when a non-LTE component is enabled to create potentialinterference with reception of downlink signals by the LTE component.The user equipment device then sends an IDC indication message to theradio network to get an appropriate solution, but instead of waiting atthe current frequency to receive the IDC response from the radionetwork, the user equipment device moves to a non-interfering downlinksignaling channel for downlink reception of interference avoidanceinstructions. The non-interfering downlink signaling channel isallocated as a carrier frequency that is safely remote from the ISM bandfor use in IDC operation to avoid potential downlink interference.

Various illustrative embodiments will now be described in detail withreference to the accompanying figures. While various details are setforth in the following description, it will be appreciated that theembodiments may be practiced without these specific details, and thatnumerous implementation-specific decisions may be made to achieve thedevice designer's specific goals, such as compliance with processtechnology or design-related constraints, which will vary from oneimplementation to another. While such a development effort might becomplex and time-consuming, it would nevertheless be a routineundertaking for those of ordinary skill in the art having the benefit ofthis disclosure. For example, selected aspects are shown in blockdiagram and flow chart form, rather than in detail, in order to avoidlimiting or obscuring the present disclosure. In addition, some portionsof the detailed descriptions provided herein are presented in terms ofalgorithms or operations on data within a computer memory. Suchdescriptions and representations are used by those skilled in the art todescribe and convey the substance of their work to others skilled in theart. Various illustrative embodiments will now be described in detailbelow with reference to the figures.

Ongoing 3GPP discussions have addressed the technical challengesassociated with addressing interference caused by concurrent operationof multiple radio technologies. The difficulties here may be understoodwith reference to the example of a single device which supports LTEtechnology with ISM (e.g., Bluetooth and/or WLAN) and/or GNSStechnologies which can interfere with one another, such as when the ISMtransmitter interferes with the LTE receiver, or when the LTEtransmitter causes interference with the ISM and GNSS receiveroperations. For example and as reported at the 3GPP report R4-102268entitled “LS on in-device coexistence interference,” the Bluetooth (BT)component error rate is unacceptable when an LTE component is active insome channels of Band 7 or even Band 40 for some BT component channelconditions. Thus, even though there is no degradation to the LTEcomponent, simultaneous operation with the BT component can result inunacceptable disruption in voice services terminating in a BT headset. Asimilar issue exists when LTE transmissions interfere with GNSScomponents. Currently, there is no RRM (Radio Resource Management)mechanism for addressing this issue since LTE by itself does notexperience any degradation. There are also interference scenarios forthe LTE components caused by the non-LTE components. For example and asreported in the 3GPP report R4-102268, the LTE downlink (DL) error ratecan be very high (44-55% on PDSCH) when the BT component is active andLTE is deployed in Band 40.

There have been attempts to address the coexistence interferenceproblems using existing radio resource management (RRM) mechanisms andsignaling procedures, such as RSRQ (Reference Signal Received Quality)measurement, inter-frequency/inter-RAT handover, cell (re)selection, RLF(Radio Link Failure) monitoring and connection (re)establishment. Themain issues and discussions are on 1) how to identify the in-devicecoexistence interference 2) how to notify the network of in-devicecoexistence interferences 3) what kind of signaling, operation andprocedures are necessary to avoid in-device coexistence interference and4) how to choose the best way, Frequency Division Multiplexing (FDM) orTime Division Multiplexing (TDM), to avoid in-device coexistenceinterferences, etc. However, existing procedures require furtherevaluation to determine if they could handle the coexistenceinterference and guarantee the required quality of service (QoS). Forexample, a normal LTE handover procedure using RRC (Radio ResourceControl) message exchange is not guaranteed to succeed when there is LTEDL interference since high DL error rates can lead to a DL Radio LinkFailure (RLF), which in turn can cause unacceptable problems when the UEattempts to re-establish the connection by accessing another frequency.

One such problem with using existing RRM mechanism is the QoSdegradation caused by delay in recovering from RLF which is supposed tobe used only in extreme scenarios and is not designed for maintainingQoS guarantee of an on-going connection. In particular and asillustrated with reference to the signal flow diagram 100 shown FIG. 1,the time to declare RLF can be quite large, depending on the networksettings of the RLF timer T310. Once the UE 10 has declared DL RLF upondetecting interference from another device radio component (e.g., ISM),the UE performs an initial search during a first measurement interval 16before sending the Out-of-Synch Indication (signal flow 1.1), shown inthis example as requiring 200 ms. Then, the UE must access a differentchannel which leads to additional delay at the source eNB 12 associatedwith the counter delay 18 from the RLF timer T310 (e.g., 1000 ms),frequency scanning delay 20 (e.g., 40 ms×k, where k is the number offrequencies), and RRC reconnection time 22 (e.g., at least 200 ms) untilsuch time as RRC connection is established via signal flow 1.2 to cell14 at the same or different eNB. In this example, RLF recovery can takeat least 1.56 sec (=200 ms+1000 ms+40 ms*k+200 ms, when k=4) todetermine and recover from radio link failure.

A number of contributions, proposals and issues have been proposed toresolve the in-device coexistence problem, but final conclusions havenot been reached. For example and as disclosed at 3GPP TR36.816v1.0.0.1: entitled “Study on signalling and procedure for interferenceavoidance for in-device coexistence” (Release 10), three differentoperation modes (“Uncoordinated,” “Coordinated within UE only” and”Coordinated within UE and Network”) and basic solutions (FDM and TDM)are proposed. In the “Uncoordinated” mode, different components withinthe same UE operate independently without any internal coordinationbetween different components (LTE, ISM and GNSS). In the “Coordinatedwithin UE only mode,” there is an internal coordination between thedifferent components within the same UE, which means that at least theactivities of one radio is known by other component's radio, however theeNB is not aware of the coexistence issue possibly experienced by the UEand is therefore not involved in the coordination. In the “Coordinatedwithin UE and with Network mode,” different components within the UE areaware of possible coexistence problems and the UE can inform the eNBabout such information and problems, so it is then mainly up to thenetwork to decide how to avoid coexistence interference. As proposed,FDM has two different possible solutions, 1) moving LTE signal away fromISM frequency band and 2) moving ISM signal away from LTE frequencyband. Based on these potential solutions and modes, some proposals anddecisions have been made as a baseline for the initial discussion andstudy, but only concept and problem in principle have been introducedand captured, and more detail solutions and proposals will be submittedand presented in the future meetings.

FDM Solutions

With FDM solutions, the UE informs the E-UTRAN whentransmission/reception of LTE or other radio signal would benefit or nolonger benefit from LTE not using certain carriers or frequencyresources. With this approach, UE judgment is taken as a baselineapproach for the FDM solution, i.e., the UE will indicate whichfrequencies are (not) useable due to in-device coexistence. Theindication can be sent by the UE whenever it has a problem in ISM DLreception it cannot solve by itself. The indication can also be sent bythe UE whenever it has a problem in LTE DL reception it cannot solve byitself, and the eNB did not take action yet based on RRM measurements.When LTE UL transmission interferes with ISM/GNSS DL reception, LTEmeasurements cannot be used to detect the problem and the details of thetrigger(s) for the UE to report the problem will probably not bespecified in 3GPP. When ISM UL transmission interferes with LTE DLreception, it needs to be determined whether more detailed LTE DLmeasurement or trigger needs to be specified (e.g., with respect to whento take the measurement in relation to ISM transmissions).

The indication from the UE that a problem occurs can be classified aseither reactive (meaning that a problem is reported only when it isdetected), or proactive (meaning that potential problems are reported).Reactive indications are supported as the baseline and it is still bedetermined whether proactive indications, which are not based on LTE DLmeasurements, should be allowed. Proactive refers to the case that theUE reports that a frequency (serving frequency or candidate frequency)may suffer from unacceptable high interference if the ISM transmitterincreases its activity. Proactive indications could be sent in thefollowing two cases: 1) the UE asks the network not to hand itself overto certain of non-serving frequencies that may experience coexistenceissues (e.g., due to increase of ISM traffic), or 2) the UE asks thenetwork to change current serving frequency because coexistence problemsmay become serious due to increased ISM traffic.

In response to the UE's indication message to the eNB that there isinterference from non-LTE components, the eNB sends a response messagewith any solution, FDM or TDM, to restore communication with the eNB.However, the response message may not be received correctly if DLreception of LTE component is severely interfered by UL transmission ofnon-LTE components.

The standards groups have not yet determined how to prevent interferencewith the response messages. To address this scenario, selectedembodiments propose the allocation of a non-interfering downlinksignaling channel which can avoid interference, though it will beappreciated that the proposal also applies to TDM solutions as describedbelow.

TDM Solutions

With TDM solutions, it is assumed that SCO, eSCO, A2DP and ACL protocolsare supported by in-device BT radio when analyzing the TDM solutions forLTE-BT coexistence. In addition, beacon, power saving and DCF protocolsare assumed to be supported by in-device WiFi radio when analyzing theTDM solutions for LTE-WiFi coexistence. For TDM solutions without UEsuggested patterns, the UE signals the necessary information (e.g.,interferer type, mode and possibly the appropriate offset) in subframesto the eNB. Based on such information, the TDM patterns (i.e.,scheduling and unscheduled periods) are configured by the eNB. For TDMsolution with UE suggested patterns, the UE suggests the patterns to theeNB, and the eNB must then decide the final TDM patterns. In 3GPPTR36.816 v1.0.0.1, there are two proposed TDM solutions—a DiscontinuousReception (DRX) based solution and H-ARQ process reservation basedsolution.

In the DRX-based solution, the UE provides the eNB with a desired TDMpattern. For example, the parameters related to the TDM pattern canconsist of (1) the periodicity of the TDM pattern, and (2) the scheduledperiod (or unscheduled period). It is up to the eNB to decide and signalthe final DRX configuration to the UE based on UE suggested TDM patternand other possible criteria (e.g., traffic type). The timing patternconsists of On-time interval for LTE component and Off-time interval fornon-LTE component. Thus, during On-time interval the LTE componenttransmits and receives the signal with the eNB whereas non-LTE componenttransmits and receives the signals with its base station (e.g., AccessPoint for WiFi and Master node for BT) during Off-time interval. In caseof data transmission, the instance of On/Off time interval are quicklyvaried and allocated due to the data transmission characteristics (e.g.Data Burstiness). However current operations cannot support this quicktiming interval transition because the On-time and Off-time intervalsare coarsely allocated by the eNB. In addition, during the On-timeinterval for the LTE component, it needs to allow for the non-LTEcomponent to transmit and receive the data if the LTE component does notoccupy the On-time interval instantaneously.

In H-ARQ process reservation-based solution, a number of LTE HARQprocesses or subframes are reserved for LTE operation, and the remainingsubframes are used to accommodate non-LTE components (e.g., ISM and/orGNSS traffic). For example, for LTE TDD UL/DL Configuration 1, subframe#1, #2, #6 and #7 are reserved for LTE usage, and other subframes may beused for non-LTE components. The UE may not be required to receivePDCCH/PDSCH and/or transmit PUSCH/PUCCH in those subframes, depending oncoexistence scenarios. It is up to the eNB to decide and signal thefinal time pattern to the UE based on some assistance informationreported by the UE. With respect to the assistance information, the UEcan indicate either:

Time offset between BT and LTE+BT configuration, or

In-device coexistence interference pattern(s), or

HARQ process reservation based pattern(s)

Since the reserved subframes can be restricted by the eNB, the eNB canrestrict DL allocation/UL grants inside this time pattern. However, anyrestrictions set by the eNB must still be signaled to the UE in aresponse message, and the standards groups have not yet determined howto prevent interference with the response messages. To address thisscenario, selected embodiments propose the allocation of anon-interfering downlink signaling channel which can avoid interference.

In selected embodiments, the disclosed signaling procedures provide acoexistence operation mode by defining new RRC signaling messages whichare exchanged between the network and the mobile device for establishingand allocating a non-interfering downlink signaling channel that may beused by the UE device to receive interference solution instructions fromthe eNB device to enable coexistence operation between LTE and non-LTEcomponents (e.g., ISM and GNSS). Alternatively, new information elementsare defined which may be inserted in existing RRC messages to establishand allocate a non-interfering downlink signaling channel for receivingdownlink instructions from the eNB device. Thus, there is no limitationor restriction to any particular application or messaging scheme sincethe functionality of the proposed messages (e.g., CoExist-REQ andCoExist-RES) could be adopted as information elements (IE) in other newor existing RRC messages (e.g., RRCConnectionReconfiguration,UEInformationRequest, RRCConnectionRequest,RRCConnectionReconfigurationComplete,RRCConnectionReestablishmentRequest, orRRCConnectionReestablishmentComplete messages). Of course, the specificnames used here are for illustration only, and other names may be usedto achieve the described function or outcome from the processing of themessage.

To illustrate the role of the non-interfering downlink signalingchannel, reference is now made to FIG. 2 which depicts a radio resourcecontrol signaling call flow 200 in accordance with selected embodimentswherein LTE and non-LTE components installed on a single UE deviceplatform exchange coexistence signaling messages to separate the LTE andnon-LTE signaling in time, thereby avoiding coexistence interference. Onthis shared platform, the LTE component on the UE 201 can know theinstance when the non-LTE component is enabled, or can otherwise detectwhen an internal request to switch to non-LTE component is initiated. Inresponse, the UE 201 can request coexistence mode operation by sendingan indication message in an uplink transmission to the eNB 202 thatin-device coexistence interference has been detected. The indicationmessage from the UE 201 can be a simple message indicating that IDCinterference has been detected, or can be a specific uplink requestmessage (e.g., CoEXIST-REQ message 2.1) to the eNB 202 with proposedcoexistence parameters. As an example, the proposed coexistenceparameters may propose a Start Time Offset, Keeping Time, On-interval,Off-interval, Possible Link, and an Action field set to “1.” If the LTEcomponent at the UE 201 is coexisting with ISM components, the PossibleLink parameter can be set to “Nothing” in order to ensure no coexistenceinterference issues. On the other hand, if the LTE component at the UE201 is coexisting with a GNSS component, the Possible Link parameter canbe set to “DL” so that the LTE component can receive messages in the DLwhile the GNSS component receiver is enabled. As will be appreciated,the LTE component at the UE 201 sends the request message to the eNB202, so the LTE component must either be “on” or at least activated inan “On-interval” during coexistence mode.

The eNB 202 responds by sending a response message at signal flow 2.2(e.g., COEXIST-RSP) in a downlink transmission to the UE 201. In generalterms, the response message 2.2 may specify the chosen solution (e.g.,FDM or TDM) from the eNB 202 to restore communication with the eNB in acoexistence mode of operation. In other embodiments, the responsemessage 2.2 may include signal control parameters defining a coexistencemode of operation with a start time, end time, and alternating intervalsof operation for the LTE and non-LTE components.

On reception, the eNB 202 sends a response message (CoExist-RSP message2.2) back to the UE 201 in response to the request message CoExist-REQ.This response message accepts or modifies the proposed coexistenceparameters from the UE's request message by returning a set of(counter-proposed) coexistence parameters defining a coexistence mode ofoperation with a start time, end time, and alternating intervals ofoperation for the LTE and non-LTE components. For example, theCoExist-RSP message may specify a Start Time Offset, Keeping Time,On-interval, Off-interval, Possible Link, and Action field set to “1.”The response message 2.2 may configure the coexistence parameters asabsolute or delta configuration values. With an absolute valueconfiguration, the eNB 202 sends all related coexistence parameters inthe response message 2.2, but with a delta value configuration, the eNB202 only sends the coexistence parameters in the response message 2.2that are different from the request message 2.1.

Based on the coexistence parameters in the response message received bythe UE 201, the LTE component may enter into a coexistence operationmode, beginning at the Start Time Offset 210 and continuing untilexpiration at the Keeping Time 218, with alternating On-intervals 212,216 (during which the LTE component is enabled) and Off-intervals 214(during which the non-LTE component is enabled).

During the coexistence mode, the LTE component at the UE 201 mayoptionally send an update message 2.3 to the eNB 202 to request that theduration of the coexistence operation mode be extended or terminated. Inselected embodiments, the update message 2.3 is a separate message(e.g., CoExistDeact-REQ message) received at the eNB 202 which seeks todeactivate or extend the coexistence operation mode, such as byterminating or extending the Keeping Time. In other embodiments, theupdate message uses the first request message (CoExist-REQ message)which has the Action field set to “0.” In either case, the updatemessage 2.3 may include update parameters, such as Start Time Offset andan Action field reset to “0,” where the updated Start Time Offset valuespecifies the new end point or Keeping Time value for the coexistenceoperation mode.

The eNB 202 responds to the update message 2.3 by sending an updateresponse 2.4 during an available On-interval. In selected embodiments,the update response 2.4 is a separate message (e.g., CoExistDeact-RSPmessage), while in other embodiments, the update message uses the firstresponse message (CoExist-RSP message) which has the Action field resetto “0.” With the update response message 2.4, the coexistence operationmode may be deactivated or extended depending on the eNB status, such asby terminating or extending the Keeping Time. And while the updateresponse 2.4 is shown as being sent in response to the update message2.3, the update response 2.4 may be sent in unsolicited manner withoutreceiving an update message. For example, the update message 2.4 can besent without solicitation if the eNB 202 determines that the coexistenceoperation mode requires extension or early termination. Once the KeepingTime 218 expires, the LTE component in the UE 201 and the eNB 202 mayreturn to normal mode where the LTE component is enabled and the non-LTEcomponent is disabled and turned-off.

Regardless of which specific coexistence mode of operation is specified,the eNB 202 conveys coexistence mode instructions to the UE 201 in oneor more downlink instructions (e.g., CoEXIST-RSP response message 2.2 or2.4). However, the reception of coexistence mode instructions at the UE201 may be impaired or prevented if DL reception of LTE component isinterfered by the UL transmission of non-LTE components. To illustratehow this problem can arise, reference is now made to Figure which 3illustrates an example spectrum band allocation 300 of LTE and non-LTEcomponents used in which a non-interfering downlink signaling channelmay be allocated to avoid interference. As will be appreciated by thoseskilled in the art, RF filter-based solutions typically suggest at least20 MHz band separation between LTE and non-LTE components. With thisfrequency separation, the LTE Band 7 307 may not induce the interferenceto BT channels 305 if the separation from the 20 MHz guard band 308 isenough for the isolation between two bands. However, the LTE Band 40 302and non-LTE component in the ISM band 304 may experience theinterference together due to adjacent band effect if there is not enoughRF filtering. For example, a non-LTE component, such as an ISM component(BT and WiFi), can interfere with an LTE component in Band 40, meaningthat DL signaling from the eNB is not guaranteed to be safely andcorrectly received by the UE when the non-LTE component is enabled. Inthe spectrum allocation 300, this is seen where a BT component operatingon Channel #1 (2402-2403 MHz) in BT band 305 will experienceinterference with LTE Band 40 302 operating on 2382-2400 MHz. Likewise,if the WiFi component in WIFI band 306 is working on the Channel #1(2401-2423 MHz), 2381-2400 MHz of LTE Band 40 in LTE band 302 may beinterfered. Also, if the WiFi component in WIFI band 306 is working onthe Channel #14 (2473-2495 MHz), 2500-2515 MHz of LTE Band 7 in LTE band307 may give interference. As a result, there are a number of knowninterferable bands 303 assuming the in-device coexistence operation andband allocation in use, meaning that the UE can be aware of the specificfrequency which can be interferable when the non-LTE components areenabled. It will also be appreciated that GNSS systems can alsoexperience interference from the LTE component because GNSS systemsgenerally operate at around 1575.42 MHz which overlaps with 2nd harmonicfrequency of LTE Band 13/14, 1554-1574 MHz/1576-1596 MHz of LTE Band 13UL (777-787 MHz) and Band 14 UL (788-798 MHz) when an LTE componenttransmits while in the GNSS is in the reception status.

With the illustrated spectrum band allocation 300, it can be seen thatthe UE may be able to successfully send an indication or request messagein an uplink transmission 310 without interference from the ISM band304, but if a response message with coexistence mode instructions issent in a downlink transmission 311 which is subject to interferencefrom the ISM band 304, the downlink signal 311 from the eNB may fail. Toprovide safe and correct DL reception from the eNB 202, anon-interfering downlink signaling channel (a.k.a., Evacuating Channel)is allocated (e.g., downlink channel 313) for use in enabling safedownlink transmission and reception of IDC-related signals when IDCinterference occurs. By reserving and allocating the non-interferingdownlink signaling channel in a portion of the spectrum that issufficiently removed from the ISM band 304, coexistence modeinstructions may be safely received at the UE over a downlinktransmission using the allocated non-interfering downlink signalingchannel. For example, a safe band 301 shown in the example spectrum bandallocation 300 is a suitable location for allocating a non-interferingdownlink signaling channel 313. With this arrangement, the LTE componenton the in-device coexistence platform may not be required to convey tothe eNB any specific operating frequency band and available channelinformation for the non-LTE component since the downlink signalingchannel in the safe band 301 is known beforehand and established withRRC signaling during the call setup procedures.

In the safe band 301, the downlink signaling channel (e.g., 313) may beused to protect the eNB's response message from the undesirableinterference. In selected embodiments, the downlink signaling channel isset as a system parameter which takes into account the different radiotechnologies installed on the UE and their associated interference bands303. In other embodiments, the eNB receives the operating frequencyrange for the LTE component and non-LTE component on the UE along withthe associated interferable frequency band (e.g., 303) based on theperformance of the RF filter installed in the UE, and uses thisinformation to determine the safe band range (e.g., 301) while anothercomponent is running. In this safe band 301, the eNB can set thefrequency boundary and allocate the downlink signaling channel 313. Asshow in FIG. 3, the downlink signaling channel (e.g., 313) should belocated far away from the interferable zone 303 to protect or minimizethe interference. In addition, the downlink signaling channel may bepart of a shared resource so long as there is capacity to send theappropriate message to affected UE within a short period of time.

As described herein, the downlink signaling channel (a.k.a., EvacuatingChannel) may be a pre-determined specific carrier frequency for IDCoperation. In selected embodiments, the eNB allocates the downlinksignaling channel only to IDC UEs (e.g., UEs having both LTE and non-LTEcomponents on a shared platform), though in other embodiments, thedownlink signaling channel may be allocated to both IDC UEs and normalUEs. For eNBs which have sufficient frequency resources in a cell (e.g.,more than a threshold number of frequency resources), the downlinksignaling channel may be reserved and allocated to IDC UEs. However, ifthe frequency resources in a cell are exhausted (e.g., below a thresholdnumber of frequency resources), the downlink signaling channel could beallocated to normal UEs which are not equipped with non-LTE components(e.g. BT, WiFi and GNSS etc.).

In allocating the downlink signaling channel, the eNB should prevent theUE from camping on the downlink signaling channel or otherwise using itfor normal operation, thereby keeping the downlink signaling channelclear for reception of response messages and interference solutioninstructions. Of course, if the eNB has alternative frequency resourcesto send response messages to the IDC UEs, the eNB may allocate thedownlink signaling channel to a normal UE. As a result, a normal UE cancamp on the downlink signaling channel when there are no IDC UEs (oronly a small number of IDC UEs) in a cell or when the eNB allocates thedownlink signaling channel to the normal UE.

Once the UE receives the response message at the downlink signalingchannel, the received interference solution instructions will guide theoperation of the UE. In some embodiments, the interference solutioninstructions received at the downlink signaling channel will cause theUE to move to another frequency or channel after taking any solution(FDM or TDM) on the downlink signaling channel. In other embodiments,the UE may return to the previous frequency which was interfered bynon-LTE component after taking TDM solution on the downlink signalingchannel. In still further embodiments, the UE may stay on the downlinksignaling channel if the downlink signaling channel is not highlyloaded.

To illustrate the operation of the process for using a downlinksignaling channel, reference is made to FIG. 4 which depicts the callflow diagram 400 illustrating the sequential movement of the UE 401 andeNB 402 from a first channel f(y) through a non-interfering downlinksignaling channel f(x) to a second channel f(z) in accordance withselected embodiments. As depicted, the UE 401 which is equipped with LTEand non-LTE components in the same platform receives a notificationmessage 404 from the eNB 402 which specifies the downlink signalingchannel f(x). As will be appreciated, the notification message 404 anddownlink signaling channel can be permanently set as a system parametersuch that the downlink signaling channel is predetermined as a permanentfrequency band for the IDC UE. Alternatively, the notification message404 and downlink signaling channel can be flexibly set with one or moreRRC signaling messages or broadcast messages such as SIBs. Thisflexibility allows the downlink signaling channel to be set according tocell loading or frequency usage so that a downlink signaling channel canbe temporarily reserved for the IDC UEs in a cell, but otherwise notreserved if there are no IDC UEs in a cell.

In selected embodiments, the notification message(s) 404 sent by the eNB402 should reflect an allocation whereby the non-interfering downlinksignaling channel f(x) is available for all IDC UEs in a cell. Ofcourse, if there are no IDC UEs in a cell or if the non-interferingdownlink signaling channel f(x) is rarely used, the eNB 402 may allocatethe non-interfering downlink signaling channel f(x) to normal UEs. Insituations where the non-interfering downlink signaling channel f(x)overloaded and there is no available resource for an IDC UE 401, the eNB402 may selectively accept a request from the IDC UE 401 based on itspriority (e.g. grade of UE) or QoS requirements.

Once in-device coexistence interference occurs (step 406), the UE 401sends an IDC indication message 408 (e.g., RRC signaling message) to theeNB 402 indicating that there is in-device coexistence interference. Atthis point, the UE 401 is operating at a first or original frequencyf(y) when IDC interference from non-LTE components is detected orscheduled, and is requesting that a new frequency f(z) be allocated atthe downlink signaling channel f(x). At this point, the UE 401 may beconfigured to measure and report information about frequencies that areavailable or unavailable for use with the UE 401 so that the eNB 402 hasan accurate understanding of the conditions at the UE 401. For example,the UE 401 may report which frequencies are available and/or notavailable for use by the UE 401 based on detected interferenceconditions. With this information, the eNB 402 is able to make moreintelligent allocation decisions by eliminating the UE's unavailablefrequencies as well as any of the UE's available frequencies that cannotbe used due to overload or any other scheduling problem at the eNB 402.From point of UE, therefore, any possible or impossible frequencies maybe reported to the eNB 402 in with the IDC indication message 408 toallow more flexible and intelligent channel allocations.

Subsequently at step 410, the UE 401 changes the working frequencychannel, f(y), to the downlink signaling channel f(x) to receive aresponse message from the eNB 402 which will include interferencesolution instructions (e.g., FDM or TDM) and possibly also a newfrequency f(z). Since the downlink signaling channel f(x) was previouslyestablished or allocated (e.g., via notification message 404), the UE isprogrammed to receive the response message 412 at the downlink signalingchannel f(x) which will specify a second or new frequency f(z).

Once the UE 401 receives the IDC indication response message 412 fromthe eNB 402, the UE 401 sends an ACK message 414 to the eNB 402 toconfirm the resource allocation (FDM/TDM and new frequency f(z)). Inthis case, ACK message could be HARQ-ACK message or L3 RRC message.After acknowledging receipt of the response message 412 (with ACKmessage 414), the UE 401 and eNB 402 can resume normal operation usingthe FDM or TDM solution at f(z) at step 416.

By using the downlink signaling channel f(x) to convey a allocatedfrequency f(z) for communications between the UE 401 and eNB 402, theeNB 402 prevents the UE 401 from occupying the downlink signalingchannel f(x). In selected embodiments, the allocated frequency f(z) maybe a new frequency so that the UE 410 moves to another, differentfrequency or channel after taking any solution (FDM or TDM) from theresponse message 412 on the downlink signaling channel f(x).Alternatively, the allocated frequency f(z) may be the previous IDCinterfered frequency f(y) so that the UE 401 moves back to the previousfrequency which was interfered by non-LTE component after taking TDMsolution from the response message 412 on the downlink signaling channelf(x). Alternatively, the allocated frequency f(z) may be the downlinksignaling channel f(x) so that the UE 401 stays on the downlinksignaling channel if it is not highly loaded.

As shown in FIG. 4, the UE 401 may be programmed to receive the responsemessage 412 within a certain transition time 409 at the downlinksignaling channel f(x) which will specify a second or new frequencyf(z). In selected embodiments, the transition time 409 for moving timefrom the interfered channel f(y) to the downlink signaling channel f(x)defines a maximum or time-out value for determining if the UE 401receives a timely indication response message 412. If the UE 401 doesnot receive the IDC response message 412 from the eNB 402 beforeexpiration of the transition time 409, the UE 401 may be configured toassume that the IDC indication message 408 was not correctly receivedover the downlink signaling channel f(x) by the eNB. In this case, theUE 401 may be configured to return back to the original frequency f(y)to re-send the IDC indication message 408, and the process repeats.Alternatively, the UE 401 may instead send the IDC indication messageone or more times over the downlink signaling channel f(x) instead ofgoing back to the original frequency f(y).

As an alternative to having the UE 401 move directly to the downlinksignaling channel f(x) after detecting in-device coexistenceinterference, the UE 401 may instead be configured to wait for apredetermined time period before moving to the downlink signalingchannel f(x). In selected embodiments, the UE 401 moves to the downlinksignaling channel f(x) if the IDC response message 412 is not receivedbefore expiration of a timer which is initiated when the UE sends thefirst IDC indication 408, where the timer value may be defined as asystem parameter or otherwise configured in the notification message404. Alternatively, the UE 401 may be configured to move to the downlinksignaling channel f(x) if a threshold number of IDC indication messagetransmissions 408 are sent without receiving an IDC response message412, where the threshold may be defined as a system parameter orotherwise configured in the notification message 404. After the UE 401moves to downlink signaling channel f(x), the UE 401 can send anotherIDC indication message or otherwise confirm that it has moved to thedownlink signaling channel f(x). In response, the eNB 402 can allocate anew frequency, f(z), with FDM or TDM solution using an IDC responsemessage, or can let the UE 401 stay at the downlink signaling channelf(x) by allowing normal data service to be resumed without sending anIDC response message.

To recover from errors that can arise when the UE 401 moves in sequencefrom one channel f(y) to another f(z) via the downlink signaling channelf(x), there are error recovery schemes proposed for both the UE 401 andthe eNB 402.

At the UE 401, the IDC indication message 408 may be sent several timesto the eNB 402 at the original frequency f(y). If the UE 401 does notreceive a response message 412 at the downlink signaling channel f(x)which contains interference avoidance instructions (e.g., FDM/TDM and anew frequency f(z)) within a predetermined transition time 409, the UE401 may be configured to go back to the original frequency f(y) tore-send the IDC indication message 408 to the eNB 402. At this time, theUE 401 may send the IDC indication message 408 one or more times at theoriginal frequency f(y), and then return to the downlink signalingchannel f(x) for DL reception (e.g. IDC indication response message)from the eNB 402. Alternatively, the UE 401 may send the IDC indicationmessage 408 one or more times at the downlink signaling channel f(x)instead of going back to the original frequency f(y). Alternatively, theUE 401 may declare a radio link failure (RLF) situation and try toreselect the cell.

At the eNB 402, error recovery may be supported by configuring the eNB402 to return back to the original frequency f(y) to wait for an IDCindication message 408 if the eNB 402 does not receive an ACK message414 from the UE 401 at the downlink signaling channel f(x) within aspecified time. If the eNB 402 receives the IDC indication message atthe original frequency f(y), it may follow the normal procedures shownin FIG. 4. But if no IDC indication message is received, the eNB 402 maynot attempt to distribute interference solution instructions.

To illustrate another example operation of the process for using adownlink signaling channel, reference is made to FIG. 5 which depictsthe call flow diagram 500 illustrating the whole movement of the UE 501and eNB 501 from a first channel f(y) through a non-interfering downlinksignaling channel f(x) to a second channel f(z) in accordance withselected embodiments. As depicted, the UE 501 is equipped with LTE andnon-LTE components in the same platform and receives a notificationmessage 504 from the eNB 502 which specifies the downlink signalingchannel f(x) in a notification message 504, either as a permanent systemparameter or via one or more RRC signaling messages or broadcastmessages which allow the downlink signaling channel to be flexibly setaccording to cell loading or frequency usage. Again, the non-interferingdownlink signaling channel f(x) may be allocated so that is availablefor all IDC UEs in a cell, or may be allocated to normal UEs if thereare no IDC UEs in a cell or if the non-interfering downlink signalingchannel f(x) is rarely used, or may be selectively allocated to an IDCUE 401 based on its priority (e.g. grade of UE) or QoS requirements incases where the non-interfering downlink signaling channel f(x)overloaded.

At step 506, the UE 501 detects the existence of in-device coexistenceinterference at the first or original frequency f(y) and at step 508,the UE 501 changes the working frequency channel, f(y), to the downlinksignaling channel f(x) to receive a response message from the eNB 502which may include interference solution instructions (e.g., FDM or TDM)and possibly also a new frequency f(z). Since the downlink signalingchannel f(x) was previously established or allocated (e.g., vianotification message 504), the UE may be programmed to move to thedownlink signaling channel f(x) which for reception of an indicationresponse message 512 which may specify a second or new frequency f(z).

At step 510, the UE 501 sends an IDC indication message 510 (e.g., RRCsignaling message) to the eNB 502 indicating that there is in-devicecoexistence interference, thus reversing the sequence of steps 406, 408shown in FIG. 4. After the channel change, the UE 501 is operating atthe downlink signaling channel f(x), and is requesting that a newfrequency f(z) be allocated at the downlink signaling channel f(x). Atthis point, the UE 501 may be configured to measure and reportinformation about frequencies that are available or unavailable for usewith the UE 501 so that the eNB 502 has an accurate understanding of theconditions at the UE 501 and can make more intelligent allocationdecisions by eliminating the UE's unavailable frequencies as well as anyof the UE's available frequencies that cannot be used due to overload orany other scheduling problem.

After moving to the downlink signaling channel f(x), the UE 5011 maysend a scheduling request message (not shown) to the eNB 502 on thesignaling channel f(x). Upon receiving a UL grant message (not shown)from the eNB 502 on the signaling channel f(x), the UE 501 transmits theIDC indication message 510 to the eNB 502 at the signaling channel f(x).In view of this possibility, the eNB 502 should monitor the signalingchannel f(x) to check for UL signals from the UE 501. Sending ofscheduling request message and receiving of UL grant message could bedone before sending the IDC indication message 510.

Once the UE 501 receives the IDC indication response message 512 fromthe eNB 512, the UE 501 sends an ACK message 514, such as a HARQ-ACKmessage or L3 RRC message, to confirm the resource allocation (FDM/TDMand new frequency f(z)). Thereafter, the UE 501 and eNB 501 can resumenormal operation using the FDM or TDM solution at f(z) at step 516.

In the example shown in FIG. 5, the eNB 502 may have load informationabout the other UEs in its cell and the associated frequency channelsused by same. With this information, the eNB 502 can allocate the dataand downlink signaling channel(s) to avoid the need for multiple channelchanges by the UEs 501. For example, the eNB 502 could use thenotification messages 504 to direct the IDC UE 501 to an alternativedownlink signaling channel f(z) if the primary downlink signalingchannel f(x) is already crowded. In addition or in the alternative, theeNB 502 could change the notification messages 504 so that, for new UEs,the primary downlink signaling channel f(x) is changed to a new primarydownlink signaling channel f(z) when the eNB 502 determines that theprimary downlink signaling channel f(x) is overcrowded. In this way, newIDC UEs that have not been allocated to channel f(x) will go to channelf(z), while the old IDC UEs continue to operate with the channel f(x).If for any reason there is a requirement that every IDC UE mustdiscontinue use of the primary downlink signaling channel f(x), the eNB502 can send out an appropriate announcement or broadcast message.

To recover from errors that can arise when the UE 501 moves wholly fromone channel f(y) to another f(z) via the downlink signaling channelf(x), there are error recovery schemes proposed for both the UE 501 andthe eNB 502.

At the UE 501, the UE 501 may be configured to send the IDC indicationmessage 510 several times to the eNB 502 at the downlink signalingchannel f(x). If the UE 501 does not receive a response message 512 atthe downlink signaling channel f(x) which contains interferenceavoidance instructions (e.g., FDM/TDM and a new frequency f(z)) within aspecified time, the UE 501 may be configured to re-send the IDCindication message 510 one or more times on the downlink signalingchannel f(x). Alternatively, the UE 501 may declare a radio link failure(RLF) situation and try to reselect the cell.

At the eNB 502, error recovery is supported by configuring the eNB 502to monitor the downlink signaling channel f(x) if the eNB 402 does notreceive an ACK message 514 from the UE 501 at the downlink signalingchannel f(x) within a specified time. Alternatively, the eNB 502 mayre-send an IDC indication response message 512 with resources allocation(FDM/TDM and new frequency) and then wait the ACK message 514 again.

An EC indication message could be newly created to indicate the downlinksignaling channel information (a.k.a., Evacuating Channel) to thein-device coexistence device. But existing RRC message or MAC CE methodcould be used for this purpose if the same information elements areadded on the message. Attached at the Appendix is an example messagestructure including proposed changes to the existingRRCConnectionReconfiguration message in TS36.331 for allocatingnon-interfering downlink signaling channel, though other existingmessages could also be used with similar logic modifications.

By now it should be appreciated that there is disclosed herein methodsfor use in a radio access network (eNB) by user equipment (UE) having afirst radio technology component (e.g., an LTE component) and a secondradio technology component (e.g., a GNSS or ISM) on a single platform.In addition, computer program products are disclosed that include anon-transitory computer readable storage medium having computer readableprogram code embodied therein with instructions which may be adapted tobe executed to implement a method for operating user equipment (UE)and/or a radio access network (eNB) in a coexistence mode, substantiallyas described hereinabove. In disclosed systems, methods, and computerprogram products, a frequency allocation scheme is provided forreceiving response message from the radio access network over anallocated downlink signaling channel for the in-device coexistencesystem in both sequential moving and whole moving embodiments. Thedownlink signaling channel is allocated to provide safe UL transmissionand DL reception at the user equipment when IDC interference occurs bybeing positioned far from the potentially interfering frequency range(e.g., ISM band) and safe from IDC interference. Whether set as a systemparameter or flexibly set with RRC signaling messages, the downlinksignaling channel is the channel for conveying interference solutionsfrom the radio network once the user equipment detects and/or signalsthe existence of IDC interference. The downlink signaling channel mayalso be used with various error recovery schemes to provide for morerobust exchange of IDC indication and response messages.

The user devices and network elements described herein may include anygeneral or special purpose computer with sufficient processing power,memory resources, and network throughput capability to handle thenecessary workload placed upon it. FIG. 6 illustrates an examplecomputer system 600 that may be suitable for implementing one or moreembodiments disclosed herein. The computer system 600 includes aprocessor 604 (which may be referred to as a central processor unit orCPU) that is in communication with input/output (I/O) devices 602,network connectivity devices 606, an optional secondary storage 608,random access memory (RAM) 610, and read only memory (ROM) 612. Theprocessor may be implemented as one or more CPU chips.

The secondary storage 608 is optionally included, and typically includesone or more disk drives or tape drives used for non-volatile storage ofdata and/or for over-flow data storage device if RAM 610 is not largeenough to hold all working data. Secondary storage 608 may be used tostore programs which are loaded into RAM 610 when such programs areselected for execution. The ROM 612 is used to store instructions andperhaps data which are read during program execution. ROM 612 is anon-volatile memory device which typically has a small memory capacityrelative to the larger memory capacity of secondary storage. The RAM 610is used to store volatile data and perhaps to store instructions. Accessto both ROM 612 and RAM 610 is typically faster than to secondarystorage 608.

I/O devices 602 may include on or more printers, video monitors, liquidcrystal displays (LCDs), touch screen displays, keyboards, keypads,switches, dials, mice, track balls, voice recognizers, card readers,paper tape readers, or other well-known input devices.

The network connectivity devices 606 may take the form of modems, modembanks, ethernet cards, universal serial bus (USB) interface cards,serial interfaces, token ring cards, fiber distributed data interface(FDDI) cards, wireless local area network (WLAN) cards, radiotransceiver cards such as code division multiple access (CDMA) and/orglobal system for mobile communications (GSM) radio transceiver cards,and other well-known network devices. These network connectivity 606devices may enable the processor 604 to communicate with an Internet orone or more intranets. With such a network connection, it iscontemplated that the processor 604 might receive information from thenetwork, or might output information to the network in the course ofperforming the above-described method steps. Such information, which isoften represented as a sequence of instructions to be executed usingprocessor 604, may be received from and outputted to the network, forexample, in the form of a computer data signal embodied in a carrierwave or a non-transitory computer readable storage medium, such as RAM,ROM or other memory storage devices.

Such information, which may include data or instructions to be executedusing processor 604 for example, may be received from and outputted tothe network, for example, in the form of a computer data baseband signalor signal embodied in a carrier wave. The baseband signal or signalembodied in the carrier wave generated by the network connectivity 606devices may propagate in or on the surface of electrical conductors, incoaxial cables, in waveguides, in optical media, for example opticalfiber, or in the air or free space. The information contained in thebaseband signal or signal embedded in the carrier wave may be orderedaccording to different sequences, as may be desirable for eitherprocessing or generating the information or transmitting or receivingthe information. The baseband signal or signal embedded in the carrierwave, or other types of signals currently used or hereafter developed,referred to herein as the transmission medium, may be generatedaccording to several methods well known to one skilled in the art.

The processor 604 executes instructions, codes, computer programs,scripts which it accesses from hard disk, floppy disk, optical disk(these various disk-based systems may all be considered secondarystorage 608), ROM 612, RAM 610, or the network connectivity devices 606.While only one processor 604 is shown, multiple processors may bepresent. Thus, while instructions may be discussed as executed by aprocessor, the instructions may be executed simultaneously, serially, orotherwise executed by one or multiple processors. In addition or in thealternative, any required processing functionality may be executed by acryptographic engine or other hardware accelerator circuit (not shown).

FIG. 7 is a diagram of a software environment 700 that may beimplemented on a communication device and/or network node operable forsome of the various embodiments of the disclosure. As illustrated, oneor more processing resources at the communication device or network nodeexecute operating system drivers 704 that provide a platform from whichthe rest of the software operates. The operating system drivers 704provide drivers for the device hardware with standardized interfacesthat are accessible to application software. The operating systemdrivers 704 include application management services (“AMS”) 706 thattransfer control between applications running on the device. In UEinstances, the software environment 702 includes a web browserapplication 708, a media player application 710, and Java applets 712are provided as device applications. The web browser application 708configures the UE device to operate as a web browser, allowing a user toenter information into forms and select links to retrieve and view webpages. The media player application 710 configures the UE to retrieveand play audio or audiovisual media. The Java applets 712 configure theUE device to provide games, utilities, and other functionality. Finally,the component 714 may provide the in-device coexistence interferencemanagement functionality described herein.

Referring now to FIG. 8, there is shown a schematic block diagramillustrating exemplary components of a mobile wireless communicationsdevice 101 which may be used with selected embodiments. The wirelessdevice 101 is shown with specific components for implementing featuresdescribed above. It is to be understood that the wireless device 101 isshown with very specific details for exemplary purposes only.

A processing device (e.g., microprocessor 128) is shown schematically ascoupled between a keyboard 114 and a display 126. The microprocessor 128controls operation of the display 126, as well as overall operation ofthe wireless device 101, in response to actuation of keys on thekeyboard 114 by a user.

The wireless device 101 has a housing that may be elongated vertically,or may take on other sizes and shapes (including clamshell housingstructures). The keyboard 114 may include a mode selection key, or otherhardware or software for switching between text entry and telephonyentry.

In addition to the microprocessor 128, other parts of the wirelessdevice 101 are shown schematically. These include a communicationssubsystem 170; a short-range communications subsystem 102; the keyboard114 and the display 126, along with other input/output devices includinga set of LEDs 104, a set of auxiliary I/O devices 106, a serial port108, a speaker 111 and a microphone 112; as well as memory devicesincluding a flash memory 116 and a Random Access Memory (RAM) 118; andvarious other device subsystems 120. The wireless device 101 may have abattery 121 to power the active elements of the wireless device 101. Thewireless device 101 is in some embodiments a two-way radio frequency(RF) communication device having voice and data communicationcapabilities. In addition, the wireless device 101 in some embodimentshas the capability to communicate with other computer systems via theInternet.

Operating system software executed by the microprocessor 128 is in someembodiments stored in a persistent store, such as the flash memory 116,but may be stored in other types of memory devices, such as a read onlymemory (ROM) or similar storage element. In addition, system software,specific device applications, or parts thereof, may be temporarilyloaded into a volatile store, such as the RAM 118. Communication signalsreceived by the wireless device 101 may also be stored to the RAM 118.

The microprocessor 128, in addition to its operating system functions,enables execution of software applications on the wireless device 101. Apredetermined set of software applications that control basic deviceoperations, such as a voice communications module 130A and a datacommunications module 130B, may be installed on the wireless device 101during manufacture. In addition, a personal information manager (PIM)application module 130C may also be installed on the wireless device 101during manufacture. The PIM application is in some embodiments capableof organizing and managing data items, such as e-mail, calendar events,voice mails, appointments, and task items. The PIM application is alsoin some embodiments capable of sending and receiving data items via awireless network 110. In some embodiments, the data items managed by thePIM application are seamlessly integrated, synchronized and updated viathe wireless network 110 with the device user's corresponding data itemsstored or associated with a host computer system. As well, additionalsoftware modules, illustrated as another software module 130N, may beinstalled during manufacture.

Communication functions, including data and voice communications, areperformed through the communication subsystem 170, and possibly throughthe short-range communications subsystem 102. The communicationsubsystem 170 includes a receiver 150, a transmitter 152 and one or moreantennas, illustrated as a receive antenna 154 and a transmit antenna156. In addition, the communication subsystem 170 includes a processingmodule, such as a digital signal processor (DSP) 158, and localoscillators (LOs) 160. In some embodiments, the communication subsystem170 includes a separate antenna arrangement (similar to the antennas 154and 156) and RF processing chip/block (similar to the Receiver 150, LOs160 and Transmitter 152) for each RAT, although a common baseband signalprocessor (similar to DSP 158) may be used for baseband processing formultiple RATs. The specific design and implementation of thecommunication subsystem 170 is dependent upon the communication networkin which the wireless device 101 is intended to operate. For example,the communication subsystem 170 of the wireless device 101 may bedesigned to operate with the Mobitex™, DataTAC™ or General Packet RadioService (GPRS) mobile data communication networks and also designed tooperate with any of a variety of voice communication networks, such asAdvanced Mobile Phone Service (AMPS), Time Division Multiple Access(TDMA), Code Division Multiple Access (CDMA), Personal CommunicationsService (PCS), Global System for Mobile Communications (GSM), etc.Examples of CDMA include 1X and 1x EV-DO. The communication subsystem170 may also be designed to operate with an 802.11 Wi-Fi network, and/oran 802.16 WiMAX network. Other types of data and voice networks, bothseparate and integrated, may also be utilized with the wireless device101.

Network access may vary depending upon the type of communication system.For example, in the Mobitex™ and DataTAC™ networks, wireless devices areregistered on the network using a unique Personal Identification Number(PIN) associated with each device. In GPRS networks, however, networkaccess is typically associated with a subscriber or user of a device. AGPRS device therefore typically has a subscriber identity module,commonly referred to as a Subscriber Identity Module (SIM) card, inorder to operate on a GPRS network.

When network registration or activation procedures have been completed,the wireless device 101 may send and receive communication signals overthe communication network 113. Signals received from the communicationnetwork 113 by the receive antenna 154 are routed to the receiver 150,which provides for signal amplification, frequency down conversion,filtering, channel selection, etc., and may also provide analog todigital conversion. Analog-to-digital conversion of the received signalallows the DSP 158 to perform more complex communication functions, suchas demodulation and decoding. In a similar manner, signals to betransmitted to the network 113 are processed (e.g., modulated andencoded) by the DSP 158 and are then provided to the transmitter 152 fordigital to analog conversion, frequency up conversion, filtering,amplification and transmission to the communication network 113 (ornetworks) via the transmit antenna 156.

In addition to processing communication signals, the DSP 158 providesfor control of the receiver 150 and the transmitter 152. For example,gains applied to communication signals in the receiver 150 and thetransmitter 152 may be adaptively controlled through automatic gaincontrol algorithms implemented in the DSP 158.

In a data communication mode, a received signal, such as a text messageor web page download, is processed by the communication subsystem 170and is input to the microprocessor 128. The received signal is thenfurther processed by the microprocessor 128 for an output to the display126, or alternatively to some other auxiliary I/O devices 106. A deviceuser may also compose data items, such as e-mail messages, using thekeyboard 114 and/or some other auxiliary I/O device 106, such as atouchpad, a rocker switch, a thumb-wheel, or some other type of inputdevice. The composed data items may then be transmitted over thecommunication network 113 via the communication subsystem 170.

In a voice communication mode, overall operation of the device issubstantially similar to the data communication mode, except thatreceived signals are output to a speaker 111, and signals fortransmission are generated by a microphone 112. Alternative voice oraudio I/O subsystems, such as a voice message recording subsystem, mayalso be implemented on the wireless device 101. In addition, the display126 may also be utilized in voice communication mode, for example, todisplay the identity of a calling party, the duration of a voice call,or other voice call related information.

The short-range communications subsystem 102 enables communicationbetween the wireless device 101 and other proximate systems or devices,which need not necessarily be similar devices. For example, the shortrange communications subsystem may include an infrared device andassociated circuits and components, or a Bluetooth™ communication moduleto provide for communication with similarly-enabled systems and devices.

By now it should be appreciated that there is disclosed herein methodsfor use in user equipment (UE) devices comprising a first radiotechnology component (e.g., an LTE component) and a second radiotechnology component (e.g., a GNSS or ISM component) on a singleplatform. In disclosed systems and methodologies, the UE may detectin-device coexistence interference at a radio component at a firstchannel frequency. At the radio component, the IDC interference can bedetected by receiving an internal message that a second radio componentis or will be enabled, or by receiving an internal message identifying atransmission frequency band being used by a second radio component, orby measuring in-device coexistence interference from a second radiocomponent. The UE device may then send a coexistence interferenceindication message to a radio access network. At this time, the UEdevice may also identify one or more available (or unavailable) channelfrequencies at the user equipment device and including identifyinginformation for the available (or unavailable) channel frequencies inthe coexistence interference indication message. The UE device may thenreceive a response message at a downlink signaling channel frequencythat is different from first channel frequency, where the responsemessage includes one or more control parameters for establishing asecond channel frequency for the radio component. In selectedembodiments, the downlink signaling channel frequency is specified as asystem parameter which defines a frequency band which is notexperiencing in-device coexistence interference, but in otherembodiments, an Radio Resource Control (RRC) message (e.g.,RRCConnectionReconfiguration) sent by the radio network is used todefine the downlink signaling channel frequency as a non-interferingfrequency band which is not interfered by a second radio component. Inother embodiments, the downlink signaling channel frequency is displacedfrom an Industrial, Science and Medical (ISM) frequency band by at leasta predetermined interference band. Using the control parameters, the UEdevice enables the radio component to use the second channel frequencywhich may be different from or the same as the downlink signalingchannel frequency.

In addition, there is disclosed methods for use in radio access network(eNB) to avoid interference between first and second radio componentslocated on a single platform at a user equipment (UE). In disclosedmethodologies, the eNB may receive a coexistence interference indicationmessage indicating the existence at a first radio component of in-devicecoexistence interference at a first channel frequency caused by a secondradio component, and may subsequently send a response message at adownlink signaling channel frequency that is different from firstchannel frequency, where the response message comprises one or morecontrol parameters for establishing a second channel frequency for thefirst radio component. The eNB may also send a Radio Resource Control(RRC) message (e.g., RRCConnectionReconfiguration message) whichspecifies the downlink signaling channel frequency to the UE. As anerror recovery operation, the eNB may return to the first channelfrequency to receive a second coexistence interference indicationmessage if an acknowledge (ACK) message to the response message is notreceived within a predetermined time period.

In another form there is disclosed computer program products implementedas a non-transitory computer readable storage medium having computerreadable program code embodied therein that may be adapted to beexecuted to implement a method for operating user equipment (UE) in acoexistence mode. As disclosed, the computer program products mayinclude instructions for detecting at the first radio componentin-device coexistence interference from the second radio component at afirst channel frequency, and then sending a coexistence interferenceindication message to a radio access network. In addition, the computerprogram products may include instructions for receiving a responsemessage at a downlink signaling channel frequency that is different fromfirst channel frequency, where the response message comprises one ormore control parameters for establishing a second channel frequency forthe first radio component. The computer program products may alsoinclude instructions for enabling the first radio component with the oneor more control parameters to use the second channel frequency withoutinterference to/from the second radio component.

In yet another form, there is disclosed user equipment devices having afirst radio technology component (e.g., an LTE component) and a secondradio technology component (e.g., a GNSS or ISM component) and methodfor operating same. As disclosed, the UE device may include processorcontrol logic and/or circuitry configured to provide a preferredfrequency notification for the first radio component to avoid in-devicecoexistence interference from the second radio component by detecting atthe first radio component in-device coexistence interference at a firstchannel frequency, and then sending a coexistence interferenceindication message to a radio access network. The processor controllogic and/or circuitry then cause the UE device to receive a responsemessage at a downlink signaling channel frequency that is different fromfirst channel frequency, where the response message comprises one ormore control parameters for establishing a second channel frequency forthe first radio component.

It should be understood that as used herein, terms such as coupled,connected, electrically connected, in signal communication, and the likemay include direct connections between components, indirect connectionsbetween components, or both, as would be apparent in the overall contextof a particular embodiment. The term coupled is intended to include, butnot be limited to, a direct electrical connection.

Numerous modifications and variations of the present application arepossible in light of the above teachings. It is therefore to beunderstood that within the scope of the appended claims, the embodimentsof the application may be practiced otherwise than as specificallydescribed herein.

Although the described exemplary embodiments disclosed herein aredescribed with reference to a coexistence operation mode wherebydifferent signaling components are separated in time to avoidcoexistence interference, the embodiments are not necessarily limited tothe example embodiments which illustrate inventive aspects that areapplicable to a wide variety of signaling schemes and applications.Thus, the particular embodiments disclosed above are illustrative onlyand should not be taken as limitations, as there may be modificationsand practices in different but equivalent manners apparent to thoseskilled in the art having the benefit of the teachings herein.Accordingly, the foregoing description is not intended to limit thedisclosure to the particular form set forth, but on the contrary, isintended to cover such alternatives, modifications and equivalents asmay be included within the spirit and scope as defined by the appendedclaims so that those skilled in the art should understand that they canmake various changes, substitutions and alterations without departingfrom the spirit and scope in its broadest form.

APPENDIX

This appendix sets forth proposed changes to selected 3GPP TS reportsand specifications that relate to the management and avoidance ofin-device coexistence interference.

APPENDIX TS 36.331 - Change for RRCConnectionReconfiguration Message forAllocating Non-Interfering Downlink Signaling Channel.=================================== Begin ofChange================================= RRCConnectionReconfigurationmessage  Signalling radio bearer: SRB1  RLC-SAP: AM  Logical channel:DCCH  Direction: E-UTRAN to UE RRCConnectionReconfiguration ::= SEQUENCE{ rrc-TransactionIdentifier RRC-TransactionIdentifier,criticalExtensions CHOICE { c1 CHOICE{ rrcConnectionReconfiguration-r8RRCConnectionReconfiguration-r8-IEs, spare7 NULL, spare6 NULL, spare5NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL },criticalExtensionsFuture SEQUENCE { } } }RRCConnectionReconfiguration-r8-IEs ::= SEQUENCE { measConfig MeasConfigOPTIONAL, -- Need ON mobilityControlInfo MobilityControlInfo OPTIONAL,-- Cond HO dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OFDedicatedInfoNAS OPTIONAL, -- Cond nonHO radioResourceConfigDedicatedRadioResourceConfigDedicated OPTIONAL, -- Cond HO- toEUTRAsecurityConfigHO SecurityConfigHO OPTIONAL, -- Cond HOnonCriticalExtension RRCConnectionReconfiguration-v890-IEs OPTIONAL }RRCConnectionReconfiguration-v890-IEs ::= SEQUENCE {lateR8NonCriticalExtension OCTET STRING OPTIONAL, -- Need OPnonCriticalExtension RRCConnectionReconfiguration-v920-IEs OPTIONAL }RRCConnectionReconfiguration-v920-IEs ::= SEQUENCE { otherConfig-r9OtherConfig-r9 OPTIONAL, -- Need ON fullConfig-r9 ENUMERATED {true}OPTIONAL, -- Cond HO-Reestab nonCriticalExtension SEQUENCE { } OPTIONAL-- Need OP } RRCConnectionReconfiguration-r10-IEs ::= SEQUENCE {measConfig MeasConfig OPTIONAL, -- Need ON mobilityControlInfoMobilityControlInfo OPTIONAL, -- Cond HO dedicatedInfoNASList SEQUENCE(SIZE(1..maxDRB)) OF DedicatedInfoNAS OPTIONAL, -- Cond nonHOradioResourceConfigDedicated RadioResourceConfigDedicated OPTIONAL, --Cond HO- toEUTRA securityConfigHO SecurityConfigHO OPTIONAL, -- Cond HOIn-DeviceCoexistenceECallocation In-deviceCoexistenceECallocationOPTIONAL, -- Cond HO nonCriticalExtensionRRCConnectionReconfiguration-v890-IEs OPTIONAL } SecurityConfigHO ::=SEQUENCE { handoverType CHOICE { intraLTE SEQUENCE {securityAlgorithmConfig SecurityAlgorithmConfig OPTIONAL, -- CondfullConfig keyChangeIndicator BOOLEAN, nextHopChainingCountNextHopChainingCount }, interRAT SEQUENCE { securityAlgorithmConfigSecurityAlgorithmConfig, nas-SecurityParamToEUTRA OCTET STRING (SIZE(6))} }, ... } -- ASN1STOP =================================== End of Change==================================

What is claimed is:
 1. A method for use in user equipment (UE) device,comprising: detecting at a radio component in-device coexistenceinterference at a first channel frequency; sending a coexistenceinterference indication message to a radio access network; and receivinga response message at a downlink signaling channel frequency that isdifferent from first channel frequency, where the response messagecomprises one or more control parameters for establishing a secondchannel frequency for the radio component.